| When utilizing intrusion detection software, monitoring components are usually dispersed throughout the network, such as when utilizing HIDS and multiple NIDS sensors. In order to leverage the capabilities of intrusion detection systems to get a complete overall view of network and host activity, these separate components must be able to report and react to activity they detect.
Non-standard or custom communication protocols do not provide the reliability and veracity required of an enterprise class intrusion detection system. An example of a custom protocol includes, but is not limited to, vendor-specific communication protocols that have not undergone IETF RFC evaluation and/or are not in common use throughout the Internet as a whole.
Application servers do not provide IDS capability. Does not apply. |
